home *** CD-ROM | disk | FTP | other *** search
- Path: newshost.mag-net.co.uk!usenet
- From: gnome@mag-net.co.uk (John Marchant)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: A500 with Ncomm - HELP REQUIRED
- Date: 2 Jan 1996 01:40:46 GMT
- Organization: Gnome's Steamware
- Sender: gnome@mag-net.co.uk (John Marchant)
- Message-ID: <2333.6574T1278T959@mag-net.co.uk>
- References: <C6QiCBALlR4wEwLt@tanybryn.demon.co.uk>
- NNTP-Posting-Host: gnome.mag-net.co.uk
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP) *UNREGISTERED*
-
-
-
- In a message on 27-Dec-95 10:00:43, Iori Wallace wrote:
-
- > My friend is setting up a sportster with ncomm on his AMIGA 500, which
- > is runnning WorkBench 1.3.
-
- > He gets to the installation screen for NComm ok, and it starts
- > installing OK onto floppy, as he doesn't have a HD, then he gets an
- > error message, 'Volume Workbench 1.3 is full', then everything stops.
-
- > Is there any way he could continue installing on another floppy disc?
- > or is there another explanation?
-
- I'm wondering why he's putting Ncomm onto the Workbench disk? There's
- not a lot of free space on that disk.
-
- If he only has one floppy drive, then he's in trouble and I doubt he can
- run any sort of comms with that. It just might be possible if he copies
- most of his Workbench disk into RAM: but there would be a lot of
- fiddling with reassignments - too lengthy to explain here.
-
- He might be able to make a copy of the Workbench disk: delete all
- unessential stuff from that: then install Ncomm onto it. But I'm still
- doubtful he'd get all Ncomm and configs onto the floppy. And you need
- some experience to know what you can delete off a Workbench (copy) disk.
-
- Now if he has _two_ floppy drives, the situation is sensible. He can
- format a floppy in df1: and then install Ncomm onto that disk. I
- imagine the way to go about it is to copy the whole Ncomm install disk
- into RAM: and then install out of RAM: onto df1: There may be problems
- if the installer script expects to be on a named floppy. In that case
- "assign <name>: ram:" should fix it. Where I wrote <name> you insert
- the disk name that Ncomm came on.
-
- I'm sure I've forgotten something. It's ages since I used Ncomm, and it
- was before we had installer scripts. I seem to remember that before you
- use Ncomm you must "assign Ncomm:" to the directory or disk where it
- lives. Otherwise it can't find it's configs and phone directory.
-
- Hope that helps.
-
- John
- -------------------------------------------------------------------
- John Marchant ('Gnome'). Bedford UK. gnome@mag-net.co.uk
- (Fidonet 2:2500/167.15) gnome@martinac.demon.co.uk
- By the time I think I've got the answer I've forgotten the question
- -------------------------------------------------------------------
-
-
-